F,Unintended proof of concept,Cowboy programming,Low maintainability,Vision basis for requirements,Effective tools rather than speed,Little work management,Agile development,Iterative development,Manual testing,Haphazard user testing,Effective cowboy programming,High level digital kanban,34,28,12,„pre-optimization is the root of all evil“ mantra – violation led to a very scalable early version of product,High code complexity led to very poor maintainability of prototype,Prototype was hacked together,10 month development period for prototype in question,Release cycle broken down into sprints,One iteration equals one release cycle,Frequent build issues with prototype,Poorly designed prototype created great technical debt and halted progress,Development included learning new tools from scratch – choosing tools fitting the task rather than relying on existing proficiencies for more rapid development.,Prototype not usable for further development,Agile development and release planning used to manage prototype development,Final product envisioned by founder,Slight use of Trello from beginning,„very light“ user story generation and planning for tasks,Poorly designed prototype highlighted need for better structure,Requirements evolve in iterations from initial basis in founder‘s vision,On-boarding of new developers difficult in part due to code complexity,Interviewee not part of product development team,No need for work oversight/tracking tools due to team size of <=5,Prototype development team of one with assistance from a second,Poorly designed prototype had to be wholly re-factored. – unplanned throw-away prototype.,Ineffective sprint planning,Lesson learnt: Prototype testing were too focussed on functionality – no statement on what should also be tested,Founding team members newly graduated from school. No prior experience with work procedures,In-house testing focuses on stability and bug hunting,Special „hardening“ sprints dedicated to bug-fixing,Cowboy programming,Earliest prototype had 6 moth development period,Founder‘s vision of final product basis for requirements,Founders tests product in the role of a user alongside other users,Ineffective documentation of architecture for prototype – diagrams drawn but not used,Hacked together prototype successful in showcasing vision and capabilities,No structured organized user testing,User testing focuses on user experience
